When a user submits a certain type of Service Request from the Self Service Portal, they get an error "Your request could not be submitted"

After checking the SilverLight logs, I found the below, but I cannot make sense of it... This request has worked fine in the past.

Error,2012-08-14 07:03:25.5973656,Failed to create request.,Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderException: Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderException: A discovery data item was rejected because the item is already bound to another Membership relationship. ---> Microsoft.EnterpriseManagement.Common.DiscoveryDataLifetimeDependencyException: A discovery data item was rejected because the item is already bound to another Membership relationship.
   at Microsoft.EnterpriseManagement.Common.Internal.ConnectorFrameworkConfigurationServiceProxy.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)
   at Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData.CommitInternal(EnterpriseManagementGroup managementGroup, Guid discoverySourceId, Boolean useOptimisticConcurrency)
   at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObjectProjection.CommitInternal(Guid discoverySourceId, Boolean useOptimisticConcurrency)
   at Microsoft.EnterpriseManagement.Common.EnterpriseManagementObjectProjection.CommitInternal(Boolean useOptimisticConcurrency)
   at Microsoft.EnterpriseManagement.ServiceManager.Portal.DataProviders.CreateRequestProvider.CreateRequest(TemplateReader requestDataObject)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.Execute(DataCommand command)
   at Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService.Execute(TransportDataCommand command)
   at SyncInvokeExecute(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContext		

I was able to resolve this myself.

• Marked as answer by TaylorNelsonCardno Tuesday, October 23, 2012 12:02 AM

I was able to resolve this myself.

• Marked as answer by TaylorNelsonCardno Tuesday, October 23, 2012 12:02 AM

I was able to resolve this myself.

• Marked as answer by TaylorNelsonCardno Tuesday, October 23, 2012 12:02 AM

I was able to resolve this myself.

• Marked as answer by TaylorNelsonCardno Tuesday, October 23, 2012 12:02 AM

I was able to resolve this myself.

Could you please fill us in with additional information?

I'm also experiencing the issue at this moment and would like to replay the steps you took to solve the issue.

I am also experiencing this issue.  If anyone has any information that will be great. 

Hello

I am not 100% sure how I resolved it, as I have experienced a plethora of issues since then.

I believe it was an issue with the RO itself, and the way I was relating a configuration item or something along those lines.

I was able to resolve this myself.

Hi,

We're also started getting that error message. Any suggestions how to fix it?

Yours
Soroush